How users are identified
HP Insights has two separate identity contexts: one for the people who administer it (system users), and one for the people who print (print users). How their configuration relates depends on whether your organization uses Legacy SSO or Admin SSO, and mixing them up is a common source of confusion during setup. This page explains both contexts, how print users authenticate, and what you'll need to decide before you configure anything.
Two identity contexts
The distinction matters because the two contexts serve different purposes and are configured in different places.
| Context | Who it covers | What it controls | Where it's configured |
|---|---|---|---|
| System users | Admins and staff with HP Insights accounts who sign in to the web console. | Access to the management console: fleet, users, policy, reporting. | Account Settings > Single Sign-On Configuration (Legacy SSO) or Account Settings > Settings > Admin SSO, depending on your organization. See below. |
| Print users | Everyone who submits and releases print jobs. | Identity for print job attribution, release authentication, and policy enforcement. | Account Settings > Settings > User Authentication Providers |
With Legacy SSO, system user sign-in and print user authentication are configured separately, and they can use different identity providers. With Admin SSO, administrator sign-in reuses the User Authentication Providers configuration that print users already use, so you configure your identity provider once. See System user authentication.
How print user authentication works
With Secure Print, a print job goes through two distinct authentication steps: identity is established at the workstation, and the user authenticates again at the printer to release the job. Administrators often focus on only one of these steps, but Secure Print needs both. Secure Print Direct uses only the first step; see Identity with Secure Print Direct.
Step 1: Identity at the workstation
When a user submits a print job, Print Scout establishes who they are. This happens silently in the background for most authentication methods. The mechanism depends on which authentication provider is configured:
OpenID Connect (OIDC)
Print Scout redirects the user to the organization's identity provider for sign-in and receives authentication tokens used to identify the user when printing.
SAML
Print Scout redirects the user to the organization's identity provider for sign-in and receives a SAML assertion that identifies the user.
With OpenID Connect and SAML, credentials stay with your identity provider. HP Insights receives an assertion of identity, not a password.
Step 2: Authentication at the printer
With Secure Print, the user authenticates again when they walk up to the printer. This is what holds the job until the right person is standing there. It's separate from Step 1, and the methods available depend on how your printers are configured:
| Method | How it works | What you need |
|---|---|---|
| Badge / proximity card | The user taps their card on a reader attached to the printer. The card is linked to their HP Insights identity during registration. | Card reader hardware on the printer. |
| QR code | The user opens the HP Secure Print mobile app and scans a QR code displayed on the printer screen or a label attached to the device. | Mobile app installed on the user's phone. |
| Passcode | A short code generated by Print Scout or the user portal. Useful as a fallback when a card is lost or unavailable. See How passcode authentication works. | Available for organizations using OIDC or SAML authentication. |
Identity with Secure Print Direct
Secure Print Direct doesn't require authentication at the printer: jobs go straight to the printer when submitted. Identity is still established at the workstation (Step 1), which is what links the job to a user in analytics and reporting.
Choosing an authentication provider
There's no universal right answer, but there's usually an obvious one once you know what you're working with.
| If your organization uses... | Use this provider | Why |
|---|---|---|
|
Microsoft Entra ID, Google, Okta, or another cloud IdP |
OpenID Connect (OIDC) | Modern SSO with token-based authentication. MFA and conditional access policies from your IdP apply automatically. |
| A SAML 2.0-capable IdP and an existing SAML infrastructure | SAML | Works with any SAML 2.0-compliant identity provider. Credentials never pass through HP Insights. |
System user authentication
By default, admins sign in to the HP Insights web console with credentials managed directly by HP Insights (internal accounts). Two SSO approaches exist, but they are mutually exclusive. Only one can be active for an organization at a time.
Legacy SSO
Configured under Account Settings > Single Sign-On Configuration. Supports Internal, SAML 2.0, and OpenID Connect. If your organization uses Legacy SSO, this tab is editable and the Admin SSO section is not visible.
Admin SSO
Configured under Account Settings > Settings > Admin SSO. This is the current approach. Unlike Legacy SSO, Admin SSO uses the Authentication Providers configuration: the same identity provider that authenticates print users can also be used for administrator sign-in, configured once. When Admin SSO is enabled for an organization, the Single Sign-On Configuration tab is still visible but shows "This feature is not applicable", and Legacy SSO can’t be configured.
How system user accounts are managed depends on the approach:
- Legacy SSO: you create and manage system users manually in Users > System Users.
- Admin SSO: system users are provisioned from your identity provider through SCIM (User and Group Sync), and Group Mapping assigns their roles. The System Users page becomes a read-only list of synced users.
User provisioning
Provisioning is how print user accounts are created and removed. There are two approaches.
Just-in-time provisioning
With OpenID Connect or SAML and Auto-Provision turned on, HP Insights creates a print user's account automatically the first time they sign in through your identity provider, from Print Scout, the mobile app, the User Portal, the Chrome extension or a secured printer. There's no pre-provisioning step: the user's identity comes from the authentication assertion.
SCIM sync
If you need accounts to exist before users print, or you want deprovisioning driven by your directory, use SCIM. Your identity provider sends user and group changes to HP Insights as users are created, modified or deactivated, and those changes are applied when they synchronize. What a deactivated user can still do after the sync depends on your HP Insights settings.
SCIM provisioning is supported for both Secure Print and Secure Print Direct. Provider support differs:
- Microsoft Entra ID: OpenID Connect and SAML.
- Okta: OpenID Connect only.
- Ping Identity: OpenID Connect only, without user groups.
See Automatic user and group provisioning with SCIM.
What users don't have to manage
With OpenID Connect or SAML, print users don't have a separate HP Insights password. They authenticate with the credentials they already use. If someone leaves and their account is disabled in your directory, they can no longer sign in through your identity provider, and if you use SCIM the deactivation is synchronized to HP Insights. There's no separate HP Insights password to reset or revoke.